Managing negotiation of power saving mode parameters between a user equipment and a core network device

ABSTRACT

The disclosed subject matter provides techniques for managing negotiation of power saving mode (PSM) parameters between a user equipment (UE) and core network device of a wireless communication network. In this regard, a method is provided that includes facilitating establishing, by a device comprising a processor, a wireless communication link with a network device of a wireless network. The method can further include, based on a determination that a power saving mode retry protocol for the device is enabled, determining, by the device, a number of times the network device previously instructed the device to use network values for power saving mode timers instead of device values for the power saving mode timers in association with the device operating in a power saving mode.

RELATED APPLICATION

The subject patent application is a continuation of, and claims priorityto each of, U.S. patent application Ser. No. 16/251,334, filed Jan. 18,2019, and entitled “MANAGING NEGOTIATION OF POWER SAVING MODE PARAMETERSBETWEEN A USER EQUIPMENT AND A CORE NETWORK DEVICE,” which is acontinuation of U.S. patent application Ser. No. 15/363,532 (now U.S.Pat. No. 10,225,802), filed Nov. 29, 2016, and entitled “MANAGINGNEGOTIATION OF POWER SAVING MODE PARAMETERS BETWEEN A USER EQUIPMENT ANDA CORE NETWORK DEVICE,” the entireties of which applications are herebyincorporated by reference herein.

TECHNICAL FIELD

The disclosed subject matter relates to techniques for managingnegotiation of power saving mode (PSM) parameters between a userequipment (UE) and a core network device.

BACKGROUND

Under the umbrella of third generation partnership project (3GPP)wireless communication technology standards, radio-access technologiesfor mobile broadband have evolved effectively to provide connectivity tobillions of subscribers and devices. Within this ecosystem, thestandardization of a radio technology for massive machine-typecommunication (MTC) applications is also evolving. A yet unfulfilled aimis for this technology to provide cost-effective connectivity tobillions of “Internet of things” (IoT) devices, to support low powerconsumption and the use of low-cost devices, and to provide excellentcoverage.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of an example wireless communication systemthat facilitates managing negotiation of PSM parameters between a UE andcore network device in accordance with various aspects and embodimentsof the subject disclosure.

FIG. 2 provides a graphical illustration demonstrating principles of PSMin accordance with various aspects and embodiments of the subjectdisclosure.

FIG. 3 provides a signaling diagram demonstrating a procedure fornegotiating PSM parameters between a UE and a core network device inaccordance with various aspects and embodiments of the subjectdisclosure.

FIG. 4 provides a flow diagram of an example method for managingnegotiation of PSM parameters between a UE and core network device inaccordance with various aspects and embodiments of the subjectdisclosure.

FIG. 5 presents an example UE configured to employ a PSM retry protocolin association with negotiating PSM parameters between the UE and thenetwork in accordance with various aspects and embodiments of thesubject disclosure.

FIG. 6 presents an example network device configured to facilitatemanaging negotiation of PSM parameters between a UE the network devicein accordance with various aspects and embodiments of the subjectdisclosure.

FIG. 7 illustrates another example method for managing negotiation ofPSM parameters between a UE and core network device in accordance withvarious aspects and embodiments of the subject disclosure.

FIG. 8 illustrates another example method for managing negotiation ofPSM parameters between a UE and core network device in accordance withvarious aspects and embodiments of the subject disclosure.

FIG. 9 illustrates another example method for managing negotiation ofPSM parameters between a UE and core network device in accordance withvarious aspects and embodiments of the subject disclosure.

FIG. 10 depicts an example schematic block diagram of a computingenvironment with which the disclosed subject matter can interact.

FIG. 11 illustrates an example block diagram of a computing systemoperable to execute the disclosed systems and methods in accordance withan embodiment.

DETAILED DESCRIPTION

One mechanism used to save user equipment (UE) power in LTE and advancedLTE cellular networks is power saving mode (PSM). The PSM process startsafter a data link between the UE and a network node is terminated orafter a periodic tracking area update (TAU) procedure completes. PSMinvolves entry into active period for a duration of time during whichthe UE remains reachable, referred to herein as idle mode (IM), followedby entry into an inactive period for a duration of time during which theUE remains unreachable, referred to herein as low power mode (LPM). Theduration of time of the IM is controlled by a first timer, referred toherein as the “active timer” and defined in 3GPP Release 12 and Release13 as (T3324). During the IM, the UE remains reachable for UE terminatedtransactions on for the duration of time defined by the active timerupon transmission from being connection to the network node to entryinto IM. In IM, UE operates according to a discontinuous reception (DRX)cycle, wherein the UE periodically activates its receiver to receivemessages from the network node. In accordance with 3GPP Release 12, thetotal duration of the IM can be from 0 seconds up to about 186 minutes.During LPM, the UE deactivates its transmitter and receiver and is thusunreachable for a defined duration of time. The duration of time the UEremains in LPM is controlled by one of two timers, referred to herein asthe LPM timer and the extended LPM (eLPM) timer, respectively. The LPMtimer and the eLPM timer are defined in the 3GGP specification Release12 as T3412 and extended T3412 (eT3412), respectively. In accordancewith 3GGP Release 12, the total duration of the LPM can be from 2seconds up to about 320 hours. In LPM, the UE remains registered in thenetwork, however the UE does not activate its receiver and thus cannotreceive messages. After the LPM duration expires, the UE can beconfigured to initiate a new TAU or ATTACH procedure with the networknode.

In this regard, PSM is a 3GPP Release 12 feature, which forms thebackbone of 3GPP's MTC power saving strategy and is a part of LTEcategory 0 (CAT-0), and CAT-M1 devices. With the PSM approach, the UEcan decide how often the UE is to be active in order to transmit andreceive data, entering PSM in between times of being active. With PSM,the UE can “sleep” in LPM for durations ranging from about 2 seconds upto 320 hours. Thus, PSM is suitable to extend the battery life of UEsthat only rarely communicate with the core network, such as low powersensor devices.

The 3GPP Release 12 allows a UE and the core network to negotiateoperating PSM parameters. In particular, with PSM, the UE and thenetwork can negotiate the PSM parameters that control the duration of IMand LMP (i.e., the active timer T3324 and the eLPM timer eT3412) tooptimize UE power consumption while balancing network signaling needs.However, current techniques employed to negotiate PSM parameters betweenthe UE and the network impart an unnecessary load on the network.

For example, if a UE supports PSM in order to enter PSM, the UE shallrequest the use of PSM during an ATTACH procedure or tracking areaupdate (TAU) procedure by including an active mode timer (T3324) valuein the request. The network accepts the use of PSM by providing aspecific value for the active timer (T3324) when accepting the ATTACH orTAU procedure request message. The UE may use PSM only if the networkhas provides a value for the active timer (T3324) in the ATTACH or TAUacceptance message that is anything but a “deactivated” value. TheATTACH or TAU acceptance message may also include a value for a LPMtimer, or an eLPM timer. If the ATTACH or TAU acceptance messagecontains the LPM timer (T3412), then the UE shall use the LPM timer(T3412) to control the duration of the LPM. If the ATTACH or TAUacceptance message contains the eLPM timer (eT3412), then the UE shalluse the eLPM timer (eT3412) to control the duration of the LPM. Ifneither a LPM timer (T3412) value nor an eLPM timer (eT3412) value isincluded in the ATTACH or TAU acceptance message, then the UE shall usethe timer value currently stored from a prior ATTACH or TAU acceptancemessage.

The 3GPP Release 12 specification facilitates negation of PSM parametersby allowing the UE to select a desired value for the active mode timer(T3324) when provided in an ATTACH or TAU request message. If the UEsupports eLPM, the UE can also include a UE selected timer value for theeLPM timer (e3412) in the ATTACH or TAU request. The UE can also requesta UE desired value for the eLPM timer (eT3412). In some scenarios, thePSM parameters provided by the network to the UE (referred to herein asthe network PSM parameters) in an ATTACH or TAU acceptance response aredifferent from the PSM parameters requested by the UE in the attach/TAUrequest (referred to herein as the UE PSM parameters). For example, a UEmay be configured to request a default maximum eLPM period (e.g., 320hours) in order to conserve power. However, based on signal schedulingconstraints, the network may determine that the UE should not apply therequested UE PSM eT3412 value, but instead apply a shorter eLPM timer(eT3412) value (e.g., about 24 hours) or regular LPM timer (T3412)value. In some implementations, the network may not provide an eLPMtimer value nor a LPM timer value. Accordingly, in some scenarios, thenetwork ATTACH or TAU acceptance response can authorize the UE tooperate using PSM but direct the UE to employ network defined PSMparameters that are different from the UE requested PSM parameters.

The 3GPP specification states the UE is to always honor the networkprovided PSM parameters, even if they are different that the PSMparameters requested by the UE. However, in this regard, the 3GPPspecification only specifies that the UE apply the network provided PSMparameters until the next attach/TAU event. For example, the 3GPPspecification specifies that the UE include PSM parameters in eachattach or TAU procedure if the UE wishes to use PSM, regardless ofwhether the UE was previously using PSM. As with the initial attach/TAUrequest, as defined in the 3GPP specification, the UE and the corenetwork can negotiate the PSM parameters in each subsequent attach/TAUrequest, even if the previous negotiation resulted in the networkproviding different PSM parameters than that requested by UE. Forexample, in every subsequent attach/TAU request sent by the UE, if theUE desires to operate using PSM, the UE can include UE desired PSMparameters in the attach/TAU request, even if the network previouslydenied usage of the UE desired PSM parameters and directed the UE to usedifferent network PSM parameters. The 3GPP specification does not definehow to manage the negotiation of PSM parameters between UE and the corenetwork. As a result, in many scenarios, there can be a continuousdeadlock wherein the UE continuously requests preferred UE PSMparameters in each attach/TAU request and the network continuouslyresponds with network PSM parameters that are different from thepreferred UE PSM parameters. This type of deadlock scenario causesunnecessary strain on the network, which can become exponentiallyexacerbated as the number of devices the network regularly negotiatesPSM parameters with grows.

The subject disclosure is directed to computer processing systems,computer-implemented methods, apparatus and/or computer program productsthat facilitate managing negotiation of PSM parameters between a UE andcore network device. For example, the subject disclosure describes amechanism that involves deploying a PSM retry protocol at the UE. Theproposed PSM retry protocol provides a solution to guide the UE/chipsetto honor the network provided PSM parameters after reaching the maximumnumber of attempts to negotiate UE preferred PSM parameters, referred toherein as a “retry” attempt. With the subject UE based PSM retryprotocol, the network can continue to control PSM parameters employed byrespective UEs serviced by the network. Thus, the network can continueto optimize network provided PSM parameters in view of both currentnetwork and current device requirements. At the same time, the networkprocessing load associated with determining whether to authorize UErequested PSM parameters in view of network logistics will be lowered.For example, after the maximum number of retry attempts is reached, theUE can be configured to stop requesting UE preferred PSM parameters inattachment and TAU requests. The UE can simply include the previouslyprovided network PSM parameters in the attachment and TAU requests. Thusthe network will not need to re-evaluate the UE requested PSM parametersand directly respond to the attachment or TAU request with the requestednetwork PSM parameters, (which the network had previously authorized theUE to employ), thereby reducing data processing and power consumption bythe network.

In addition, the subject retry mechanism allows the network to controlthe PSM retry protocol employed by the UE based on network load. Forexample, the network can control enabling and disabling the PSM retryprotocol as well as the maximum number off retry attempts allowed. Insome embodiments, the PSM retry protocol can be implemented on thenetwork provided/configured subscriber identity module (SIM) card oruniversal integrated circuit card (UICC) of the UE. According to theseembodiments, the network can control the PSM retry protocol using overthe air (OTA) messaging protocol. From the UE side, the UE will beginusing network preferred PSM parameters after a certain number of retryattempts. The UE can further log information regarding network preferredPSM parameters. This logged information can be sent to and employed bychipset vendors or device vendors to analyze and optimize their designfor certain applications.

In one or more embodiments, a method is provided that includesfacilitating establishing, by a device comprising a processor, awireless communication link with a network device of a wireless network.The method further includes, based on a determination that a powersaving mode retry protocol for the device is enabled, determining, bythe device, a number of times the network device previously instructedthe device to use network values for PSM timers instead of device valuesfor the PSM timers in association with the device operating in a PSM. Insome implementations the method can further include, in response to adetermination that the number of times does not exceed a threshold retrynumber, sending, by the device to the network device, a request to usethe device values for the PSM timers in association with the deviceoperating in the PSM. In an aspect, the sending the request comprisessending an attachment message to the network device via the wirelesscommunication link, and wherein the attachment request comprises thedevice values for the PSM timers. In another aspect, the sending therequest comprises sending a TAU message to the network device via thewireless communication link, and wherein the TAU message comprises thedevice values for the PSM timers.

In other implementations, the method can further include, in response adetermination that the number of times exceeds a threshold retry number,sending, by the device to the network device, a request to use thenetwork values for the PSM timers in association with the deviceoperating in the PSM. In accordance with various embodiments, thenetwork values for the PSM timers were previously received by the devicefrom the network device in response to a previous request, sent by thedevice to the network device, for authorization to use the device valuesfor the PSM timers in association with the device operating in the PSM,and wherein the device previously employed the network values for thePSM timers in association with the device operating in the PSM.

In another embodiment, an integrated circuit card device is providedthat comprises a processor, and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations. These operations can comprise, based on adetermination that a PSM retry protocol is enabled, determining a numberof times that a device, operatively coupled to the integrated circuitcard device, was previously instructed by a network device of a wirelesscommunication network to use a network value for a PSM parameter insteadof a device value for the PSM parameter in connection with the deviceoperating in a PSM. These operations can further comprise, directing thedevice to send a request to the network device requesting usage of thedevice value in connection with the operating in the PSM based on thenumber being determined to be less than a threshold retry number, anddirecting the device to send a second request to the network devicerequesting usage of the network value in connection with the operatingin the PSM based on the number being determined to be greater than orequal to the threshold retry number. In some embodiments, the integratedcircuit card device is a SIM card of the device. In other embodiments,the integrated circuit card device is a UICC of the device.

In yet another embodiment a machine-readable storage medium, comprisingexecutable instructions that, when executed by a processor of a device,facilitate performance of operations. These operations can includedetermining a number of times the device was previously instructed by anetwork device of a wireless communication network to use a networktimer value for a PSM instead of a device timer value for the PSM whenthe device is operating in the PSM. The operations further comprise,sending a first request to the network device requesting usage of thedevice timer value for when the device is operating in the PSM based onthe number being determined to be less than a threshold retry number. Invarious implementations, the operations can further comprise, sending asecond request to the network device requesting usage of the networktimer value for when the device operating in the PSM based on the numberbeing determined to be less greater than or equal to the threshold retrynumber.

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. The following description and the annexed drawings set forthin detail certain illustrative aspects of the subject matter. However,these aspects are indicative of but a few of the various ways in whichthe principles of the subject matter can be employed. Other aspects,advantages, and novel features of the disclosed subject matter willbecome apparent from the following detailed description when consideredin conjunction with the provided drawings. In the following description,for purposes of explanation, numerous specific details are set forth inorder to provide a thorough understanding of the subject disclosure. Itmay be evident, however, that the subject disclosure may be practicedwithout these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order tofacilitate describing the subject disclosure.

FIG. 1 is an illustration of an example wireless communication system100 that facilitates managing negotiation of PSM parameters between a UEand core network device in accordance with various aspects andembodiments of the subject disclosure. Aspects of the systems,apparatuses or processes explained in this disclosure can constitutemachine-executable component(s) embodied within machine(s), e.g.,embodied in one or more computer readable mediums (or media) associatedwith one or more machines. Such component(s), when executed by the oneor more machines, e.g., computer(s), computing device(s), virtualmachine(s), etc. can cause the machine(s) to perform the operationsdescribed.

The wireless communication system 100 can be or include various types ofdisparate networks, including but not limited to: cellular networks,femto networks, picocell networks, microcell networks, internet protocol(IP) networks Wi-Fi service networks, broadband service network,enterprise networks, cloud based networks, and the like. System 100 cancomprise one or more UEs 102, a network node 104 and a core wirelesscommunication network 106. It should be appreciated that a single UE 102is depicted for exemplary purposes and that any number of UEs can beincluded in system 100. The UE 102 can include a variety of differentmobile and stationary device types that can be configured to operateusing PSM and the subject PSM retry protocol. For example, the UE 102can include but is not limited to: a cellular phone, a smartphone, atablet computer, a wearable device, a virtual reality (VR) device, aheads-up display (HUD) device, and the like. In various exemplaryembodiments, the UE 102 can be configured with MTC or machine to machine(M2M) capabilities. For example, PSM will have a strong impact on MTCdevices (e.g., Cat-M1, Cat-M2 devices, narrowband (NB)-IoT devices,Cat-0 devices, Cat-1 devices and the like). For example, the UE 102 canbe or include metering devices, implantable medical device (IMDs),sensor and/or control devices associated with home automation systems,tracking devices, point of sale devices (e.g., vending, machines),security devices (e.g., associated with surveillance systems, homessecurity, access control, etc.), and the like. The terms MTC and M2M areused herein interchanged. A UE that is configured to perform one or moreMTC functionalities is referred to herein as an MTC device.

The UE 102 can be configured to communicate with the core wirelesscommunication network 106, and more particularly one or more networkdevices 108 of the core wireless communication network 106, using acommunication link established between the UE 102 and a network node 104of the wireless communication network. The network node 104 can beconnected to the core wireless communication network 106 (or one or morenetwork devices 108 of the core wireless communication network 106) viaone or more backhaul links (indicated by the thick arrow line). Forexample, the one or more backhaul links can include wired linkcomponents, such as but not limited to: like a T1/E1 phone line, adigital subscriber line (DSL) (e.g., either synchronous orasynchronous), an asymmetric DSL (ADSL), an optical fiber backbone, acoaxial cable, and the like. The one or more backhaul links can alsoinclude wireless link components, such as but not limited to,line-of-sight (LOS) or non-LOS links which can include terrestrialair-interfaces or deep space links (e.g., satellite communication linksfor navigation). The thin solid arrow line from the UE 102 to thenetwork node 104 represents uplink communications and the thin dashedarrow line from the network node 104 to the UE 102 represents downlinkcommunications. Communication links between a UE and a network accesspoint device, such as network node 104, are referred to herein asmachine-to-network (M2N) communication links. In some implementations,the UE 102 can be configured to communicate with one or more other UEsanother using a machine-to-machine (M2M) link. Further, in someimplementations, a UE 102 can serve as a network access point device toother UEs via which the other UEs can communicate with the network node104.

The non-limiting term network node (or radio network node) is usedherein to refer to any type of network node serving a UE 102 and/orconnected to other network node, network element, or another networknode from which the UE 102 can receive a radio signal. Examples ofnetwork nodes (e.g., network node 104) can include but are not limitedto: NodeB devices, base station (BS) devices, access point (AP) devices,and radio access network (RAN) devices. The network node 104 can alsoinclude multi-standard radio (MSR) radio node devices, including but notlimited to: an MSR BS, an eNode B, a network controller, a radio networkcontroller (RNC), a base station controller (BSC), a relay, a donor nodecontrolling relay, a base transceiver station (BTS), a transmissionpoint, a transmission nodes, an RRU, an RRH, nodes in distributedantenna system (DAS), and the like.

The wireless communication system 100 can employ various wirelesscommunication technologies and modulation schemes to facilitate wirelessradio communications between devices (e.g., between UEs 102 and betweenUEs 102 and the network node 104, between the network node 104 and oneor more network devices 108, etc.). For example, the UEs 102 can beconfigured to communicate with the network node 104, and vice versausing various wireless communication technologies, including but notlimited to: Universal Mobile Telecommunications System (UMTS)technologies, LTE technologies, advanced LTE technologies (includingvoice over LTE or VoLTE), narrowband IoT (NB-IoT), Code DivisionMultiple Access (CDMA) technologies, Time Division Multiple Access(TDMA) technologies, Orthogonal Frequency Division Multiplexing (OFDN)technologies, Filter Bank Multicarrier (FBMC) technologies, WirelessFidelity (Wi-Fi) technologies, Worldwide Interoperability for MicrowaveAccess (WiMAX) technologies, General Packet Radio Service (GPRS)technologies, Enhanced GPRS, technologies, Second Generation PartnershipProject (2GPP) technologies, 3GPP technologies, Fourth GenerationPartnership Project (4GPP) technologies, Fifth Generation PartnershipProject (5GPP) technologies, Ultra Mobile Broadband (UMB) technologies,High Speed Packet Access (HSPA) technologies, Evolved High Speed PacketAccess (HSPA+), High-Speed Downlink Packet Access (HSDPA) technologies,High-Speed Uplink Packet Access (HSUPA) technologies, ZIGBEE®technologies, or another IEEE 802.XX technology. Additionally,substantially all aspects disclosed herein can be exploited in legacytelecommunication technologies. In some embodiments, the UEs can beconfigured to communicate with one another (e.g., via M2M links) usingsuitable local area network (LAN) or personal area network (PAN)communication technologies and configured to communicate with thenetwork node 104 using suitable WAN communication technologies. Forexample, in one or more embodiments, the UEs 102 can be configured tocommunicate with one another using BLUETOOTH®, BLUETOOTH® low energy(BLE), near field communication (NFC), Wi-Fi protocol, ZIGBEE®, RF4CE,WirelessHART, 6LoWPAN, Z-Wave, ANT, and the like. The one or more UEs102 can be further configured to communicate with the network node 104using one or more of the radio access network (RAN) technologies listedabove (e.g., LTE, VoLTE, UMTS, etc.).

The core wireless communication network 106 can include various networkdevices 108 that facilitate providing wireless communication services tothe UEs 102 via the network node 104 and/or various additional networkdevices (not shown). For example, the one or more network devices 108 ofthe core wireless communication network 106 can include but are notlimited to: mobile switching center (MSCs) devices, a home locationregister (HLR) device, a visitor location register (VLR) device,authentication center (AUC) devices, provisioning servers, billingservers, operation and support system (OSS) devices, short messageservice center (SMSC) devices, and many other elements. In someimplementations, the one or more network devices 108 includes a mobilitymanagement entity (MME) device. For example, the system architectureevolution (SAE) is the core network architecture of 3GPP's LTE wirelesscommunication standard. In accordance with SAE, the MME is the keycontrol-node for the LTE access-network. The MME is involved in thebearer activation/deactivation process and is also responsible forchoosing the serving gateway (SGW) for a UE at the initial attach, theTAU procedure, and at time of intra-LTE handover involving core network(CN) node relocation. The MME is also responsible for idle mode UEpaging and tagging procedure including retransmissions. In variousembodiments, the MME can also be configured to control PSM parameternegotiation between the UE and the core wireless communication network106 in accordance with various aspects and embodiments disclosed herein.

In accordance with various aspects and embodiments described herein,system 100 can be configured to facilitate managing PSM parameternegotiation between the UE 102 and the core wireless communicationnetwork 106 that provides at least some wireless communication servicesto the UE via an M2N connection between the UE 102 and the network node104. In one or more embodiments, the UE 102 is configured to operateusing IM and PSM.

FIG. 2 provides a graphical illustration 200 demonstrating principles ofPSM in accordance with various aspects and embodiments of the subjectdisclosure. The PSM is an operating mode between transmission eventswherein the UE operates in an IM for a short period of time (e.g., 0seconds to 186 minutes) following completion of a communication sessionwith a network node, and then enters a LPM for another duration of time(e.g., from 2 seconds to 320 hours), during which the UE turns off itstransmitter and receiver for an extended sleep period. Accordingly, atotal duration of the PSM can range from 0 seconds to about 13.5 days.The IM is an operating mode in which the UE alternates betweenactivating and deactivating its receiver, (an operating mode alsoreferred to as discontinuous reception or DRX). During IM, the UElistens for paging messages or messages sent via downlink controlchannels used by the network to reach the UE. The duration of timeassociated with each receiver activation/deactivation event is referredto as the DRX period or cycle. The duration of the IM is controlled bythe active timer (T3324). In various embodiments, the active timerreflects a number of DRX cycles and a duration of the respective DRXcycles. In some implementations the DRX cycle duration is less thanabout 2.56 seconds). In one or more embodiments, the active timer cannotbe less than two DRX cycles and 10 seconds. According to theseembodiments, if the UE requested active timer (T3324) is less than thisduration, the UE can be configured to automatically increase the activetimer duration to be two DRX cycles plus 10 seconds. The LPM is anoperating mode in which the UE “sleeps” to conserve power bydeactivating its transmitter and receiver, thus operating in anunreachable state. The duration of the LPM is controlled by a LPM timer,which can be an eLPM timer (eT3412) or a regular LPM timer (T3412). Theterm PSM parameters is used herein to refer to parameters related toboth active timer (T3312), and the LPM timer (eT3412 or T3412).

FIG. 3 provides a signaling diagram 300 demonstrating a procedure fornegotiating PSM parameters between a UE and a core network device inaccordance with various aspects and embodiments of the subjectdisclosure. In the embodiment shown, the core network device includes anMME device. An eNodeB (eNB) serves as the network node (e.g., networknode 104) that communicatively connects the UE with the MME.

As described in 3GPP Release 12, in order to enter PSM, the UE shallrequest the use of PSM during an ATTACH procedure or TAU procedure byincluding PSM parameters in the attach request or the TAU request, asshown in signaling event 302. As described above, the PSM parametersmust include a value for the active timer (t3324) if the UE desires touse PSM mode. If the UE supports eLPM, the PSM parameters may(optionally) include a value for the eLPM timer (e3412) that controls aduration of the LPM. In some embodiments, the PSM parameters can alsoinclude information that controls the duration and/or number of the DRXperiods of the IM. In many implementations, the PSM parameters providedby the UE in the ATTACH or TAU request are UE PSM parameter values thatare desired or preferred by the UE. For example, the UE preferred PSMparameter values can include default UE PSM parameters values programmedinto the UE. In another example, the UE preferred PSM parameter valuescan include PSM parameter values determined by the UE based on variousoperations of the UE. In other implementations, as described in greaterdetail infra, the PSM parameter values provided by the UE in theattach/TAU request will include previously provided network PSMparameter values if the UE has reached the maximum amount of PSMnegotiation retries.

The network can authorize a UE to operate using PSM by responding to theUE attach or TAU request and including PSM parameter values in theresponse, as shown in signaling event 304. These network provided PSMparameters will include at least a value for the active timer (T3324).In some implementations, the PSM parameters will also include a valuefor the LPM timer (e.g., either T3412 or eT3412). In otherimplementations, the network ATTACH/TAU acceptance message may notinclude either a T3412 or eT3412 value). The UE then disconnects fromthe eNB as shown in signaling event 306 (e.g., via a radio resourcecontrol (RCC) connection release) and at 308 begins operating in the IMaccording to the active timer value (e.g., t3324) included in thenetwork provided PSM parameter values received from the MME in theattach/TAU accept message. Then after the IM duration timer has expired,at 310, the UE enters the LPM for the duration defined by the networkprovided LPM timber value (e.g., eT3412 or T3412) included in the PSMparameter values received from the MME in the attach/TAU accept message.If the network ATTACH/TAU acceptance message does not include an eT3412or T3412 value, the UE can be configured to employ a previously receivedor applied LPM timer value (e.g., the most recently network provided LPMtimer). In particular, as defined in 3GPP Release 12 (e.g., TS 24.301),the UE shall only operate using PSM if the network provides PSMparameters when accepting an attach request or TAU request and the UEshall always honor the network provided PSM parameter values.

With reference to FIGS. 1, 2 and 3, in some scenarios, the network PSMparameter values provided to the UE 102 by the network device (e.g., anetwork device 108, such as an MME device) in an attachment or TAUacceptance response (e.g., signaling event 304) are different from thePSM parameter values requested by the UE in the attach/TAU request. The3GPP specification specifies that the UE 102 is to always honor thenetwork provided PSM parameters, even if they are different that the PSMparameters requested by the UE. However, the 3GPP specification onlyspecifies that the UE 102 apply the network provided PSM parametersuntil the next attach/TAU event. For example, according to the 3GPPspecification, in every subsequent attach/TAU request sent by the UE102, if the UE desires to operate using PSM, the UE 102 can include UEdesired PSM parameters in the attach/TAU request, even if the networkpreviously denied usage of the UE desired PSM parameters and directedthe UE to use different network PSM parameters. The 3GPP specificationdoes not define how to manage the negotiation of PSM parameters betweenUE and the core network. As a result, in many scenarios, there can be acontinuous deadlock wherein the UE continuously requests preferred UEPSM parameters in each attach/TAU request and the network continuouslyresponds with network PSM parameters that are different from thepreferred UE PSM parameters. This type of deadlock scenario causesunnecessary strain on the network, which can be exponentiallyexacerbated as the number of devices the network regularly negotiatesPSM parameters with grows.

In order to mitigate the aforementioned deadlock scenario, in accordancewith various embodiments of the subject disclosure, the UE 102 inassociation with being configured to operate using PSM, the UE canfurther be configured with a PSM retry control functionality. The PSMretry control functionality can provide a PSM retry protocol that whenexecuted by a processor of the UE 102, controls the maximum number oftimes the UE 102 can negotiate UE desired PSM parameters with the corewireless communication network 106, (e.g., via a network device 108 ofthe core wireless communication network 106, such as an MME device),after the network has previously instructed the UE 102 to use networkPSM parameters that are different from the UE requested PSM parameters.In one or more embodiments, the retry control functionality can controlthe maximum number of times, referred to herein as N-max, that the UEcan negotiate the active timer value that controls the duration of theIM (i.e., T3324). The retry control functionality can also control themaximum number of times, referred to herein as M-max, that the UE cannegotiate a second timer value that controls the duration of the LPM(i.e., the eT3412 value).

For example, in accordance with the PSM retry control protocol, the UE102 can track the number of times the UE requests UE preferred PSMparameter values (e.g., for T3324 and/or eT3412) in attach and TAUprocedures yet is directed by the network 106 to employ network PSMparameter values (e.g., for T3324 and/or eT3412) that are different fromthe UE requested PSM parameter values. In association with each newattach or TAU procedure, based on the PSM retry control protocol, the UE102 can determine whether the number of times (the retry number N and/orM) that the UE was directed by the core wireless communication network106 to employ network PSM parameters after requesting different UE PSMparameters is greater than or equal to the maximum retry amount (themaximum retry number N-max and/or M-max). If the retry number is notgreater than or equal to the maximum retry number, then the UE 102 caninclude its preferred UE PSM parameters in the attach or TAU request.However, if the retry number is greater than or equal to the maximumretry number, based on the retry protocol, the UE can be configured toinclude the previously provided network PSM parameters in the attach orTAU request. As a result, in response to reception of the attach or TAUrequest, the core wireless communication network 106 (e.g., a networkdevice 108 of the core wireless communication network 106, such as anMME device) will not need to determine whether the network shouldauthorize the UE to apply its requested UE PSM parameters. The networkwill merely see the UE is requesting usage of PSM parameters that havealready been authorized by the network, skip the negotiation process,and direct the UE to employ the requested network PSM parameters in thenetworks attach accept or TAU accept message. The UE 102 can alsocontinue to provide the network PSM parameters in each subsequent attachor TAU request if the UE desires to operate using PSM unless the UE ispower cycled, re-booted, reset, enters and exits airplane mode or thelike, which can result in setting current retry number count back to itsdefault value (e.g., zero).

In addition, in some embodiments, the core wireless communicationnetwork 106 can control the PSM retry protocol employed by the UE basedon network load, signal scheduling constraints, UE power and servicerequirements, and other possible factors. For example, the network cancontrol enabling and disabling the PSM retry protocol on the UE as wellas the maximum number off retry attempts allowed one or more of the PSMparameters. For instance, the network can control the maximum number oftimes the UE can negotiate the first timer that controls the IM duration(N-max). The network can also control the maximum number of times the UEcan negotiate the second time that controls the duration of the PSM(M-max). In another example, the core wireless communication network 106can reset the number of UE PSM retry negotiation attempts (e.g., N orM). In some embodiments, the PSM retry protocol can be implemented onthe network provided/configured subscriber identity module (SIM) card oruniversal integrated circuit card (UICC) of the UE. According to theseembodiments, the core wireless communication network 106 can control thePSM retry protocol of the UE using over the air (OTA) messagingprotocol. For example, the UE can include a SIM card or UICC that hasbeen programmed to include the subject PSM retry control functionality.In one implementation, the PSM retry control functionality can includean PSM retry flag that can be set to one of two possible values, whereina first value (e.g., one) can enable the PSM retry functionality and asecond value (e.g., zero) can disable the PSM retry functionality. Thecore wireless communication network 106 can further control enablementand disablement of the PSM retry functionality of the UE 102 by sendingthe UE an OTA message, via a communication link established between thenetwork node 104 and the UE 102, that directs the UE to set the retryflag to either the first value or the second value. In anotherimplementation, the PSM retry control protocol on the UE SIM/UICC candefine a value for N-max and/or M-max and the core wirelesscommunication network 106 can also set the value for N-max and/or M-maxusing an OTA message sent to the UE 102.

FIG. 4 provides a flow diagram of an example method 400 for managingnegotiation of PSM parameters between a UE and core network device inaccordance with various aspects and embodiments of the subjectdisclosure. In one or more embodiments, method 400 is performed by a UE(e.g., UE 102) in association with operating in a wireless communicationnetwork (e.g., system 100). In accordance with method 400, the UE isconfigured to operate using eLPM in association with PSM. Accordingly,the UE can negotiate both the active timer (eT3324) value and the eLPMtimer (eT3412) value with the network in accordance with the subjectretry protocol. Repetitive description of like elements employed inrespective embodiments is omitted for sake of brevity.

At 402, the UE initiates an ATTACH or TAU procedure 402. For example,the UE can activate its transmitter and receiver and establish awireless communication link with a network node (e.g., network node 104)of a wireless communication network that the UE is subscribed to orotherwise authorized to connect to. In association with initiating theATTACH or TAU procedure, at 404, the UE determines whether a PSM retryprotocol functionality of the UE is enabled. For example, the UE cancheck to see whether a PSM retry flag of the UE is set to an enabledvalue (e.g., one) or a disabled value (e.g., zero). If the PSM retryprotocol is disabled, then the UE can forgo performance of the subjectPSM retry control protocol and include UE preferred PSM parameter valuesin the attach or TAU request, as indicated at 406. If however the PSMretry protocol is enabled, then at 408, the UE determines whether thenumber of active timer negotiation retries (N) exceeds N-max (e.g., themaximum number of active timer (t3324) negotiation retries the UE isauthorized to perform). If at 408, N does not exceed N-max, then the UEcan include a UE preferred active timer value in the ATTACH or TAUrequest, as indicated at 410. If however N does exceed N-max, then at412, the UE will include the previously provided network active timervalue in the ATTACH or TAU request. Then at 414, the UE determineswhether the number of eLPM timer negotiation retries (M) exceeds M-max(e.g., the maximum number of eLPM timer (eT3412) value negotiationretries the UE is authorized to perform). If at 414, M does not exceedM-max, then the UE can include a UE preferred eLPM timer value in theATTACH or TAU request, as indicated at 416. If however M does exceedM-max, then at 418, the UE will include the previously provided networkeLPM or LPM timer value in the ATTACH or TAU request.

FIG. 5 presents an example UE 500 configured to employ a PSM retryprotocol in association with negotiating PSM parameters between the UEand the network in accordance with various aspects and embodiments ofthe subject disclosure. In various embodiments, the UE 102 of system 100can be or include UE 500, or vice versa. Repetitive description of likeelements employed in respective embodiments is omitted for sake ofbrevity.

The UE can include memory 502 configured to store computer executablecomponents and instructions. For example, in various embodiments, thesecomputer executable components and instructions can include one or morePSM components 504. The one or more PSM components 504 can includeinformation and instructions that control one or more defined PSMoperations of the UE. For example, the PSM components 504 can includeinformation and instructions regarding when the UE should employ PSM. Inanother example, the PSM components 504 can include information andinstructions that define preferred or default UE PSM parameter values,such as a preferred active timer and eLPM timer values for the IM periodand the LPM period, respectively. In another example, the PSM components504 can include information and instructions that control how the UE canexecute PSM, such as instructions regarding how to request PSM in anATTACH or TAU request, and how to enter into PSM based on reception ofattach or TAU acceptance messages including network PSM parameters. TheUE 500 can also include a processor 506 to facilitate operation of theinstructions (e.g., the computer executable components and instructions)by the UE (e.g., the one or more PSM components 504). The UE 500 furtherincludes a communication component 508, a power source 510, anintegrated circuit (IC) card 514 and a device bus 512. The device bus512 can couple the various components of the UE 500 including, but notlimited to, the memory 502, the processor 506, the communicationcomponent 508, the power source 510, and the IC card 514. Examples ofsaid processor 506 and memory 502, as well as other suitable computer orcomputing-based elements that can be employed by the UE, can be foundwith reference to FIG. 11.

The communication component 508 can facilitate wireless communicationbetween the UE and other devices, such as between the UE 500 and otherUEs via an M2M link and/or between the UE 500 and a wirelesscommunication system network node (e.g., network node 104). Thecommunication component 508 can be or include hardware (e.g., a centralprocessing unit (CPU), one or more transmitters, one or more receivers,one or more transceivers, one or more decoders), software (e.g., a setof threads, a set of processes, software in execution) or a combinationof hardware and software that facilitates one or more of the varioustypes of wireless communications described herein. The power source 510can provide power to the various electrical components of the UE 500 tofacilitate operation thereof (e.g., the processor 506, the communicationcomponent 508, the IC card 514, etc.). The power source 510 can include,but is not limited to, a battery, a capacitor, a charge pump, amechanically derived power source (e.g., microelectromechanical systems(MEMs) device), or an induction component.

The IC card 514 can include a fixed or removable integrated circuitchip. The IC card can include memory 516 that stores information andcomputer executable components or instructions. In the embodiment shown,these computer executable components can include the PSM retry component518. In other embodiments, the PSM retry component 518 (and/or one ormore sub-components of the PSM retry component 518) can be provided inmemory 502. In another embodiment, one or more of the PSM components 504can be provided in memory 516 of the IC card 514. In some embodiments,the IC card 514 can include a micro-processor 526 to facilitateoperation of at least some the instructions stored in the memory 516(e.g., the PSM retry component 518). In other embodiments, the UE can beconfigured to employ processor 506 to execute the instructions stored inmemory 516 (e.g., the PSM retry component 518).

In one or more embodiments, the IC card 514 is a SIM card or a UICC thatstores network subscriber data (not shown) that includesnetwork-specific information used to authenticate and identify asubscriber on a wireless communication network (e.g., system 100). Theterms SIM card and UICC are used herein interchangeably to refer to anintegrated circuit card that provides same or similar features andfunctionalities when employed in association with a UE that isconfigured to operate using a wireless communication network. Ingeneral, the SIM card and the UICC can contain unique information thatidentifies a UE to a wireless communication network with which the SIMcard or UICC is registered and enables the UE to operate using thewireless communication network. For example, the network subscriber datacan include but is not limited to, a unique serial number (ICCID)associated with the subscriber, an IMEI number associated with thesubscriber, security authentication and ciphering information, temporaryinformation related to the local network, a list of the services thesubscriber has access to, and password information (e.g., a personalidentification number (PIN) for ordinary use, and a personal unblockingcode (PUK) for PIN unlocking. The UICC is considered a next generationSIM card and has applications beyond GSM networks. In addition tostoring network subscriber data, the IC card 514 can include one or moreSIM application toolkit (STK) or card application toolkit (CAT)applications that consist of a set of commands programmed into theSIM/UICC card which define how the SIM/UICC should interact directlywith the outside world and initiates commands independently of the UEand the network. This enables the SIM/UICC to build up an interactiveexchange between a network application and the end user and access orcontrol access to the network. In one or more embodiments, at least oneof these STK or CAT applications can be or include the PSM retrycomponent 518.

In accordance with various embodiments, the PSM retry component 518 canprovide the subject PSM retry protocol that controls the maximum numberof times the UE 102 can negotiate UE desired PSM parameters with thecore wireless communication network (via a network device 108 of thecore wireless communication network 106, such as an MME device), afterthe network has previously instructed the UE 102 to use network PSMparameters that are different from the UE requested PSM parameters. Forexample, these PSM parameters can include the active timer value (T3324)and the eLPM timer value (eT3412). Thus the PSM retry control component518 can control the maximum number of times the UE can negotiate the IMtimer value (N-max) and/or the maximum number of times the UE cannegotiate the PSM timer value (M-max). In some implementations, the PSMretry component 518 and be enabled or disabled, wherein when enabled,the UE is be configured to execute the PSM retry protocol (e.g., usingmicro-processor 526 or processor 506), and wherein when disabled, the UEis be configured to negotiate PSM parameters without the subject PSMretry protocol (e.g., according to the protocol defined by the one ormore PSM components 504). For example, the PSM retry component 518 caninclude a retry flag that can be set to a first value (e.g., one) toenable the PSM retry functionality of the PSM retry component 518 or asecond value (e.g., zero) to disable the PSM retry functionality. In oneor more embodiments, the core wireless communication network (e.g., anetwork device 108 of the core wireless communication network 106) cancontrol enabling and disabling the PSM retry component 518 using an OTAmessage.

In various embodiments, the PSM retry component 518 can include retrytracking component 520, PSM parameter control component 522, and PSMparameter information 524. When the PSM retry component 518 is enabled,the retry tracking component 520 can be configured to track the numberof times the UE sends an attach or TAU request with UE preferredparameters yet is instructed by the network, via the attach or TAUacceptance message, to employ network PSM parameters that are differentfrom the UE requested PSM parameters. For example, the retry trackingcomponent 518 can track the number of times N the UE requests a UEpreferred or default active timer (T3324) value and the number of timesM the UE requests a UE preferred or default eLPM timer (eT3412) value.The retry tracking component 520 can further store information regardingthe number of “failed” PSM negotiation attempts with respect to the IMtimer value (N) and the number of “failed” PSM negotiation attempts withrespect to the PSM timer value (M), in memory 516 (e.g., as PSMparameter information 524). In some implementations, the informationregarding the number of failed PSM negotiation attempts can merelyinclude the tracked numbers N and M. In other implementations, the retrytracking component 520 can further store information in memory 516(e.g., as PSM parameter information 524), that identifies the specificnetwork provided PSM parameter values that were applied by the UE inresponse to the failed PSM negotiation procedure. For example, the PSMparameter information 524 can also include the network provided activetimer value for the IM and/or network provided eLPM or LPM timer value.The retry tracking component 520 can also store, as PSM parameterinformation, information identifying the UE preferred PSM parametervalues that were rejected by the network (e.g., the UE preferred activetime and/or eLPM timer values).

The PSM parameter control component 522 can be configured to controlwhat PSM parameters the UE provides in each attach or TAU request. Forexample, each time the UE initiates an attach or TAU request, when thePSM retry component 518 is enabled, the PSM parameter control component522 can determine whether the value N (included in the PSM parameterinformation 524) is greater than or equal to N-max. The value N-max canalso be included in memory 516 (e.g., in the PSM parameter information524) and accessible to the PSM parameter control component 522. In someimplementations, the network (e.g., core wireless communication network106) can set the value N-max. For example, the network can send the UE500 an OTA message that that directs the UE 500 to set N-max to aspecific value (e.g., 5). In response to a determination that N is lessthan N-max, the PSM parameter control component 522 can direct orauthorize the UE to include a UE preferred active timer (T3324) value inthe attach/TAU request. However, in response to a determination that Nis greater than or equal to N-max, the PSM parameter control component522 can direct the UE to include, in the attach/TAU request, the networkactive timer (T3324) value that was most recently previously provided tothe UE by the network and employed by the UE. Information identifyingthe most recently previously provided and employed network eLPM timer(eT3412) or LPM timer (T3412) value can be stored in memory 516 (e.g.,as PSM parameter information 524).

In addition, each time the UE initiates an attach or TAU request, whenthe PSM retry component 518 is enabled, the PSM parameter controlcomponent 522 can also determine whether the value M (included in thePSM parameter information 524) is greater than or equal to M-max. Thevalue M-max can also be included in memory 516 (e.g., in the PSMparameter information 524) and accessible to the PSM parameter controlcomponent 522. In some implementations, the network (e.g., core wirelesscommunication network 106) can set the value M-max. For example, thenetwork can send the UE 500 an OTA message that that directs the UE 500to set M-max to a specific value (e.g., 5). In response to adetermination that M is less than M-max, the PSM parameter controlcomponent 522 can direct or authorize the UE to include a UE preferredeLPM timer (eT3412) value in the attach/TAU request. However, inresponse to a determination that M is greater than or equal to M-max,the PSM parameter control component 522 can direct the UE to include, inthe attach/TAU request, the network eLPM timer (eT3412) or LPM timer(T3412) value that was most recently previously provided to the UE bythe network and employed by the UE. Information identifying the mostrecently previously provided and employed network eLPM or LPM timervalue can be stored in memory 516 (e.g., as PSM parameter information524).

The retry tracking component 520 can further be configured to reset thecounts for N and/or M to default values (e.g., zero) in response to a UEreset, power recycle, re-boot, enter/exit airplane mode, and the like.In some implementations, the core wireless communication network canalso reset the counts for N and/or M to their default values or anothervalue (e.g., using an OTA message). For example, in one implementation,the network may determine that the UE should forgo any possibleremaining PSM parameter negotiation attempts allowed and begin onlyusing the network PSM parameter values. According to thisimplementation, the network can send the UE an OTA message that causesthe UE to increase N and M to be greater than the N-max and the M-maxvalue, respectively, or to set the N-max and the M-max values to valuesthat are lower than the current N and M values, respectively.

In some implementations, the network can also provide the UE with newnetwork PSM parameter values. For example, the network may respond to aUE attach or TAU request comprising network PSM parameters with anattach/TAU acceptance message with new network PSM parameters. Accordingto this implementation, as defined in the 3GGP Release 12 specification,the UE is to honor the new network PSM parameters included in theattach/TAU response. Accordingly, the UE will operate in IM and LPMaccording to the new network PSM parameters. In addition, the retrytracking component 520 can include information in the PSM parameterinformation 524 identifying the new network PSM parameters. In the nextattach/TAU request, the PSM parameter control component 522 can directthe UE to employ the new network PSM parameters if N is greater than orequal to N-max and/or M is greater than or equal to M-max.

FIG. 6 presents an example network device 600 configured to facilitatemanaging negotiation of PSM parameters between a UE the network devicein accordance with various aspects and embodiments of the subjectdisclosure. In various embodiments, a network device of the one or morenetwork devices 108 of system 100 can be or include network device 600,or vice versa. In one implementation, the network device 600 is an MMEdevice. Still in other embodiments, one or more components of thenetwork device 600 can be included at the network node (e.g., networknode) that connects a UE to the core wireless communication network(e.g., core wireless communication network 106). Repetitive descriptionof like elements employed in respective embodiments is omitted for sakeof brevity.

The network device 600 can include various components that facilitatemanaging negotiation of PSM parameters between the network device 600and a UE (e.g., UE 102, UE 500 and the like). These components caninclude PSM retry control component 602, request reception component604, requested PSM parameter evaluation component 606, PSM parameterassignment component 608 and PSM parameter tracking component 612. Thenetwork device 600 can include memory to store computer executablecomponents and instructions (e.g., the PSM retry control component 602,the request reception component 604, the requested PSM parameterevaluation component 606, the PSM parameter assignment component 608,and the PSM parameter tracking component 612). The network device 600can also include a processor 614 to facilitate operation of the computerexecutable instructions (e.g., the computer executable components andinstructions) by the network device 600. The network device 600 canfurther include a device bus 610 that couples the various components ofthe network device, including, but not limited to: the PSM retry controlcomponent 602, the request reception component 604, the requested PSMparameter evaluation component 606, the PSM parameter assignmentcomponent 608, and the PSM parameter tracking component 612, the memory616 and the processor 614. Examples of said processor 614 and memory616, as well as other suitable computer or computing-based elements thatcan be employed by the network device 600, can be found with referenceto FIG. 11.

In one or more embodiments, the PSM retry control component 602 can beconfigured to control various aspects of the PSM retry control protocoldeployed at respective UEs (e.g., on the UE SIM/UICC) serviced by thewireless communication network associated with the network device 600.For example, in some implementations, the PSM retry control component602 can control activating/enabling and deactivating/disabling the PSMretry protocol functionality at respective UEs. In embodiments in whichthe PSM retry control protocol functionality is provided on the SIM cardor UICC of the UE, the PSM retry control component 602 can direct thenetwork device 600 to send the UE an OTA message that either activatesor deactivates the retry control functionality at the UE (e.g., the PSMretry component 518). For example, the OTA message can direct the UEeither to set an PSM retry control flag value to zero or one, therebydisabling or enabling the PSM retry component 518. The PSM retry controlcomponent 602 can also control the threshold values N-max and/or M-maxemployed by the UE PSM retry component (e.g., PSM retry component 518).For example, in embodiments in which the PSM retry control protocolfunctionality is provided on the SIM card or UICC of the UE, the PSMretry control component 602 can direct the network device 600 to sendthe UE an OTA message that defines the N-max value and/or the M-maxvalue for application by the PSM retry component (e.g., PSM retrycomponent 518). In some embodiments, the PSM retry control component 602can also control resetting N and/or M back to their default values(e.g., zero) or another value.

The request reception component 604 can be configured to receive attachand TAU requests sent by a UE. In response to a determination that anattach or TAU request comprises PSM parameter values and thus includes arequest to enter PSM by the UE, the request reception component 604 canforward the request to the requested PSM parameter evaluation component606. The requested PSM parameter evaluation component 606 can beconfigured to evaluate PSM parameters included in a UE attach or TAUrequest to determine whether to authorize performance of PSM by the UE.Based on a determination that the UE is authorized to operate in PSM,the requested PSM parameter evaluation component 606 can further beconfigured to determine what PSM parameter values the UE can apply. Forexample, the PSM parameter evaluation component 606 can determine avalue for the active timer (T3324) and a value for the LPM timer (e.g.,eT3412 or T3412).

In accordance with one or more embodiments, the network device 600 canstore UE PSM parameter information 618 in memory 616 to facilitatedetermining what PSM parameters the UE can apply. For example, the UEPSM parameter information can include a look-up table that identifiesUEs service by the network device 600. The look-up table can alsoinclude information that identifies network PSM parameters that thenetwork has previously determined the UE should apply when operating inPSM, including an active timer value (e.g., T3324) and a LPM timer value(e.g., eT3412 or T3412). For example, in response to reception of anattach or TAU request from a UE including PSM parameter values, therequested PSM parameter evaluation component 606 can be configured toexamine the UE PSM parameter information 618 to determine whether the UEis included in the look-up table and whether the UE is associated withnetwork PSM parameter information.

In implementations in which the UE is included in the look-up table andis associated with network PSM parameter information, the requested PSMparameter evaluation component 606 can compare the requested UE PSMparameter value(s) for the active timer (T3324) and the LPM timer(eT3412) with the network PSM parameter values for the active timer andthe LPM timer (e.g., either eT3412 or T3412) associated with the UE. Inresponse to a determination that the requested UE PSM parameter valuesand the network PSM parameter values are the same, the requested PSMparameter evaluation component 606 can direct the PSM parameterassignment component 608 to send the UE an attach or TAU acceptancemessage including the network PSM parameter values. However, in responseto a determination that the requested UE PSM parameter values and thenetwork PSM parameter values are different, the requested PSM parameterevaluation component 606 can be configured to perform an evaluationprocess to determine whether to authorize the UE to employ the requestedUE PSM parameter values. For example, the requested PSM parameterevaluation component 606 determine whether application of the UE PSMparameter values by the UE is suitable in view of current network load(e.g., or load of the network device 600), current network signalscheduling constraints, and other network related factors.

Based on this evaluation process, in response to a determination by therequested PSM parameter evaluation component 606 that the UE can employits requested UE PSM parameter values (e.g., for the active timer and/orthe LPM timer), the requested PSM parameter evaluation component 606 candirect the PSM parameter assignment component 608 to send the UE anattach or TAU acceptance message including the requested UE PSMparameter values. However, if the requested PSM parameter evaluationcomponent 606 determines that the requested UE PSM parameter values arenot appropriate, in one embodiment, the requested PSM parameterevaluation component 606 can direct the PSM parameter assignmentcomponent 608 to send the UE an attach or TAU acceptance messageincluding the network PSM parameter values that are defined in thelook-up table. In another embodiment, the requested PSM parameterevaluation component 606 can determine new network PSM parameter valuesthat the UE should employ in view of current network conditions.According to this embodiment, the requested PSM parameter evaluationcomponent 606 can direct the PSM parameter assignment component 608 tosend the UE an attach or TAU acceptance message including the newnetwork PSM parameter values. The PSM parameter tracking component 612can further update the look-up table to include the new network PSMparameter values for the UE.

In implementations in which the UE is not included in the look-up tableand/or is not associated with network PSM parameter information, therequested PSM parameter evaluation component 606 can be configured toperform the aforementioned evaluation process to determine whether toauthorize the UE to use the UE requested PSM parameter values. Accordingto this implementation, based on the evaluation process, in response toa determination that the UE can employ its requested UE PSM parametervalues, the requested PSM parameter evaluation component 606 can directthe PSM parameter assignment component 608 to send the UE an attach orTAU acceptance message including the requested UE PSM parameter values.The PSM parameter tracking component 612 can further enter informationinto the look-up table (e.g., the UE PSM parameter information 618),associating the UE with the assigned PSM parameter values. However, ifthe requested PSM parameter evaluation component 606 determines that therequested UE PSM parameter values are not appropriate in view of currentnetwork conditions, (e.g., based on network load, signal schedulingconstraints, etc.), the requested PSM parameter evaluation component 606can determine network approved PSM parameter values that the UE shouldemploy in view of current network conditions. The requested PSMparameter evaluation component 606 can then direct the PSM parameterassignment component 608 to send the UE an attach or TAU acceptancemessage including the network determined PSM parameter values. The PSMparameter tracking component 612 can further update the look-up table toinclude information associating the UE with the network determined PSMparameter values.

With the subject configuration, if a UE provides the network device 600with PSM parameter values (e.g., for T3324 and/or eT3412 or T3412) thatare the same as those associated with the UE in the UE PSM parameterinformation 618 (e.g., the UE provides network PSM parameter values asopposed to UE preferred PSM parameter values), the requested PSMparameter evaluation component 606 does not need to perform anevaluation process to determine whether to authorize the UE requestedPSM parameter values. The PSM parameter assignment component 608 cansimply respond to the attach or TAU request with the same parametersrequested by the UE. In one or more additional embodiments, in thesescenarios, rather than always responding to the UE with the previouslyapproved network PSM parameters, the requested PSM parameter evaluationcomponent 606 can be configured to periodically re-evaluate the networkPSM parameters requested by the UE.

For example, in one embodiment, the requested PSM parameter evaluationcomponent 606 can be configured to re-evaluate the network PSMparameters requested by the UE according to a predetermined schedule(e.g., once a day, once a week, etc.). In another example, the requestedPSM evaluation component 606 can be configured to re-evaluate thenetwork PSM parameters requested by the UE in response to a change innetwork conditions, such as change in network load relative to athreshold degree of deviation. In another example, the PSM parametertracking component 612 can be configured to track the number of times Pa UE includes network PSM parameters in an attach or TAU request,thereby causing the PSM parameter assignment component 608 toautomatically respond to the request by including the network PSMparameters in the attach or TAU response. According to this example, therequested PSM evaluation component 606 can employ a threshold number(P-max) that limits the number of times the PSM parameter assignmentcomponent 608 can automatically respond with the network PSM parametervalues before re-evaluating the network PSM parameter values. Forexample, in association with reception of an ATTACH or TAU request froma UE including network PSM parameter values, if P is greater than P-max,the requested PSM parameter evaluation component 606 can be configuredto re-evaluate the network PSM parameters requested by the UE. Accordingto this example, the requested PSM parameter evaluation component 606may determine new network PSM parameter values for the UE, update thelook-up table with the new network PSM parameter values, and direct thePSM parameter assignment component 608 to send the UE and attach or TAUresponse with the new network PSM parameter values.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIGS. 7-9. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, two or more of the disclosed example methods can be implemented incombination with each other, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methodsdisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 7 illustrates another example method 700 for managing negotiationof PSM parameters between a UE and core network device in accordancewith various aspects and embodiments of the subject disclosure.Repetitive description of like elements employed in respectiveembodiments is omitted for sake of brevity.

At 702, a device comprising a processor (e.g., a UE 102, UE 500 or thelike), establishes a wireless communication link with a network deviceof a wireless network. For example, the UE can connect to a core networkdevice (e.g., a network device 108, 600 or the like), via a network nodeof the wireless communication network in association with performing anattachment procedure or a TAU procedure. At 704, the device determines,based on a determination that a PSM retry protocol for the device isenabled (e.g., based on enablement of PSM retry component 518), a numberof times (N and/or M) the network device has previously instructed thedevice to use a network value for a PSM parameter instead of a devicevalue for the PSM parameter in association with the device operating ina PSM. For example, the UE can determine a number of times (N) thenetwork device has previously instructed the UE to employ a networkactive timer (T3324) value as opposed to a UE preferred active timervalue. In another example, the UE can determine a number of times (M)the network device has previously instructed the UE to employ a networkLPM timer (e.g., T3412 or eT3412) as opposed to a UE preferred LPM timervalue (e.g., for eT3412). In one implementation, if N is less thanN-max, the UE can request usage or the UE preferred IM timer in theattachment or TAU request. Otherwise, the UE can be configured toinclude the previously received network IM timer value attachment o TAUrequest. Similarly, if M is less than M-max, the UE can request usage orthe UE preferred PSM timer in the attachment or TAU request. Otherwise,the UE can be configured to include the previously received network PSMtimer value attachment o TAU request.

FIG. 8 illustrates another example method 800 for managing negotiationof PSM parameters between a UE and core network device in accordancewith various aspects and embodiments of the subject disclosure.Repetitive description of like elements employed in respectiveembodiments is omitted for sake of brevity.

At 802, a device comprising a processor (e.g., a UE 102, UE 500 or thelike), determines a number of times (M) the device was previouslyinstructed by a network device (e.g., a network device 108, networkdevice 600 and the like) of a wireless communication network to use anetwork timer value for a PSM instead of a device timer value for thePSM in association with the device operating in the PSM. At 804, thedevice sends a first request to the network device requesting usage ofthe device timer value in association with the device operating in thePSM based on the number being less than a threshold retry number(M-max). At 806, the device sends a second request to the network devicerequesting usage of the network timer value in association with thedevice operating in the PSM based on the number being greater than orequal to the threshold retry number.

FIG. 9 illustrates another example method 900 for managing negotiationof PSM parameters between a UE and core network device in accordancewith various aspects and embodiments of the subject disclosure.Repetitive description of like elements employed in respectiveembodiments is omitted for sake of brevity.

At 902, an integrated circuit card device comprising a processor (e.g.,IC card 514), activates a PSM retry control protocol based on reception,by a device operatively coupled to the integrated circuit card device(e.g., UE 500), of an OTA message from a network device (e.g., networkdevice 108, 600 and the like) of a wireless communication network,wherein the over the air message comprises retry control informationdirecting the integrated circuit card device to activate the PSM retrycontrol protocol and defining a threshold retry number (N-max and/orM-max). At 904, based on the activating, the integrated circuit carddevice determines a number of times (N and/or M) the device waspreviously instructed by a network device of a wireless communicationnetwork to use a network value for a PSM parameter instead of a devicevalue for the PSM parameter in association with the device operating ina PSM. At 906, the integrated circuit card device directs the device tosend a first request to the network device requesting usage of thedevice value in association with the operating in the PSM based on thenumber being less than the threshold retry number. At 908, theintegrated circuit card device directs the device to send a secondrequest to the network device requesting usage of the network value inassociation with the operating in the PSM based on the number beinggreater than or equal to the threshold retry number.

FIG. 10 is a schematic block diagram of a computing environment 1000with which the disclosed subject matter can interact. The system 1000comprises one or more remote component(s) 1010. The remote component(s)1010 can be hardware and/or software (e.g., threads, processes,computing devices). In some embodiments, remote component(s) 1010 cancomprise servers, personal servers, wireless telecommunication networkdevices, RAN device(s), etc. As an example, remote component(s) 1010 canbe network node 104, network devices 108, network device 600 and thelike. The system 1000 also comprises one or more local component(s)1020. The local component(s) 1020 can be hardware and/or software (e.g.,threads, processes, computing devices). In some embodiments, localcomponent(s) 1020 can comprise, for example, UE 102, UE 500, and thelike.

One possible communication between a remote component(s) 1010 and alocal component(s) 1020 can be in the form of a data packet adapted tobe transmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 1010 and a localcomponent(s) 1020 can be in the form of circuit-switched data adapted tobe transmitted between two or more computer processes in radio timeslots. The system 1000 comprises a communication framework 1040 that canbe employed to facilitate communications between the remote component(s)1010 and the local component(s) 1020, and can comprise an air interface,e.g., Uu interface of a UMTS network, via an LTE network, etc. Remotecomponent(s) 1010 can be operably connected to one or more remote datastore(s) 1050, such as a hard drive, solid state drive, SIM card, devicememory, etc., that can be employed to store information on the remotecomponent(s) 1010 side of communication framework 1040. Similarly, localcomponent(s) 1020 can be operably connected to one or more local datastore(s) 1030, that can be employed to store information on the localcomponent(s) 1020 side of communication framework 1040.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 11, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules comprise routines,programs, components, data structures, etc. that performs particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can comprise both volatile and nonvolatilememory, by way of illustration, and not limitation, volatile memory 1120(see below), non-volatile memory 1122 (see below), disk storage 1124(see below), and memory storage 1146 (see below). Further, nonvolatilememory can be included in read only memory, programmable read onlymemory, electrically programmable read only memory, electricallyerasable read only memory, or flash memory. Volatile memory can compriserandom access memory, which acts as external cache memory. By way ofillustration and not limitation, random access memory is available inmany forms such as synchronous random access memory, dynamic randomaccess memory, synchronous dynamic random access memory, double datarate synchronous dynamic random access memory, enhanced synchronousdynamic random access memory, Synchlink dynamic random access memory,and direct Rambus random access memory. Additionally, the disclosedmemory components of systems or methods herein are intended to comprise,without being limited to comprising, these and any other suitable typesof memory.

Moreover, it is noted that the disclosed subject matter can be practicedwith other computer system configurations, comprising single-processoror multiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., personal digital assistant, phone, watch, tablet computers,notebook computers, . . . ), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network; however, some if not all aspects ofthe subject disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules can be located inboth local and remote memory storage devices.

FIG. 11 illustrates a block diagram of a computing system 1100 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1112, which can be, for example, a UE (e.g., UE 102and 500), a network node (e.g., network node 104), a core network device(e.g., network device 108, network device 600 and the like) comprises aprocessing unit 1114, a system memory 1116, and a system bus 1118.System bus 1118 couples system components comprising, but not limitedto, system memory 1116 to processing unit 1114. Processing unit 1114 canbe any of various available processors. Dual microprocessors and othermultiprocessor architectures also can be employed as processing unit1114.

System bus 1118 can be any of several types of bus structure(s)comprising a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures comprising, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire (Institute of Electricaland Electronics Engineers 11104), and small computer systems interface.

System memory 1116 can comprise volatile memory 1120 and nonvolatilememory 1122. A basic input/output system, containing routines totransfer information between elements within computer 1112, such asduring start-up, can be stored in nonvolatile memory 1122. By way ofillustration, and not limitation, nonvolatile memory 1122 can compriseread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable read only memory,or flash memory. Volatile memory 1120 comprises read only memory, whichacts as external cache memory. By way of illustration and notlimitation, read only memory is available in many forms such assynchronous random access memory, dynamic read only memory, synchronousdynamic read only memory, double data rate synchronous dynamic read onlymemory, enhanced synchronous dynamic read only memory, Synchlink dynamicread only memory, Rambus direct read only memory, direct Rambus dynamicread only memory, and Rambus dynamic read only memory.

Computer 1112 can also comprise removable/non-removable,volatile/non-volatile computer storage media. FIG. 11 illustrates, forexample, disk storage 1124. Disk storage 1124 comprises, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1124 can comprise storage media separately or in combination with otherstorage media comprising, but not limited to, an optical disk drive suchas a compact disk read only memory device, compact disk recordabledrive, compact disk rewritable drive or a digital versatile disk readonly memory. To facilitate connection of the disk storage devices 1124to system bus 1118, a removable or non-removable interface is typicallyused, such as interface 1126.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, read only memory, programmable readonly memory, electrically programmable read only memory, electricallyerasable read only memory, flash memory or other memory technology,compact disk read only memory, digital versatile disk or other opticaldisk storage, magnetic cassettes, magnetic tape, magnetic disk storageor other magnetic storage devices, or other tangible media which can beused to store desired information. In this regard, the term “tangible”herein as may be applied to storage, memory or computer-readable media,is to be understood to exclude only propagating intangible signals perse as a modifier and does not relinquish coverage of all standardstorage, memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can comprisenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium. As such, for example, a computer-readable medium can compriseexecutable instructions stored thereon that, in response to execution,cause a system comprising a processor to perform operations, comprisinggenerating an RRC connection release message further comprisingalterative band channel data.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and comprises any informationdelivery or transport media. The term “modulated data signal” or signalsrefers to a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in one or moresignals. By way of example, and not limitation, communication mediacomprise wired media, such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media.

It can be noted that FIG. 11 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1100. Such software comprises an operating system1128. Operating system 1128, which can be stored on disk storage 1124,acts to control and allocate resources of computer system 1112. Systemapplications 1130 take advantage of the management of resources byoperating system 1128 through program modules 1132 and program data 1134stored either in system memory 1116 or on disk storage 1124. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1112 throughinput device(s) 1136. In some embodiments, a user interface can allowentry of user preference information, etc., and can be embodied in atouch sensitive display panel, a mouse/pointer input to a graphical userinterface (GUI), a command line controlled interface, etc., allowing auser to interact with computer 1112. Input devices 1136 comprise, butare not limited to, a pointing device such as a mouse, trackball,stylus, touch pad, keyboard, microphone, joystick, game pad, satellitedish, scanner, TV tuner card, digital camera, digital video camera, webcamera, cell phone, smartphone, tablet computer, etc. These and otherinput devices connect to processing unit 1114 through system bus 1118 byway of interface port(s) 1138. Interface port(s) 1138 comprise, forexample, a serial port, a parallel port, a game port, a universal serialbus, an infrared port, a Bluetooth port, an IP port, or a logical portassociated with a wireless service, etc. Output device(s) 1140 use someof the same type of ports as input device(s) 1136.

Thus, for example, a universal serial bus port can be used to provideinput to computer 1112 and to output information from computer 1112 toan output device 1140. Output adapter 1142 is provided to illustratethat there are some output devices 1140 like monitors, speakers, andprinters, among other output devices 1140, which use special adapters.Output adapters 1142 comprise, by way of illustration and notlimitation, video and sound cards that provide means of connectionbetween output device 1140 and system bus 1118. It should be noted thatother devices and/or systems of devices provide both input and outputcapabilities such as remote computer(s) 1144.

Computer 1112 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1144. Remote computer(s) 1144 can be a personal computer, a server, arouter, a network PC, cloud storage, a cloud service, code executing ina cloud-computing environment, a workstation, a microprocessor basedappliance, a peer device, or other common network node and the like, andtypically comprises many or all of the elements described relative tocomputer 1112. A cloud computing environment, the cloud, or othersimilar terms can refer to computing that can share processing resourcesand data to one or more computer and/or other device(s) on an on demandbasis to enable access to a shared pool of configurable computingresources that can be provisioned and released readily. Cloud computingand storage solutions can storing and/or processing data in third-partydata centers which can leverage an economy of scale and can viewaccessing computing resources via a cloud service in a manner similar toa subscribing to an electric utility to access electrical energy, atelephone utility to access telephonic services, etc.

For purposes of brevity, only a memory storage device 1146 isillustrated with remote computer(s) 1144. Remote computer(s) 1144 islogically connected to computer 1112 through a network interface 1148and then physically connected by way of communication connection 1150.Network interface 1148 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies comprise fiber distributed data interface, copperdistributed data interface, Ethernet, Token Ring and the like. Wide areanetwork technologies comprise, but are not limited to, point-to-pointlinks, circuit-switching networks like integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines. As noted below, wireless technologies may be used inaddition to or in place of the foregoing.

Communication connection(s) 1150 refer(s) to hardware/software employedto connect network interface 1148 to bus 1118. While communicationconnection 1150 is shown for illustrative clarity inside computer 1112,it can also be external to computer 1112. The hardware/software forconnection to network interface 1148 can comprise, for example, internaland external technologies such as modems, comprising regular telephonegrade modems, cable modems and digital subscriber line modems,integrated services digital network adapters, and Ethernet cards.

The above description of illustrated embodiments of the subjectdisclosure, comprising what is described in the Abstract, is notintended to be exhaustive or to limit the disclosed embodiments to theprecise forms disclosed. While specific embodiments and examples aredescribed herein for illustrative purposes, various modifications arepossible that are considered within the scope of such embodiments andexamples, as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures such as, but not limited to,molecular and quantum-dot based transistors, switches and gates, inorder to optimize space usage or enhance performance of user equipment.A processor may also be implemented as a combination of computingprocessing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can comprise a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Further, the term “include” is intended to be employed as an open orinclusive term, rather than a closed or exclusive term. The term“include” can be substituted with the term “comprising” and is to betreated with similar scope, unless otherwise explicitly used otherwise.As an example, “a basket of fruit including an apple” is to be treatedwith the same breadth of scope as, “a basket of fruit comprising anapple.”

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point,” “base station,”“Node B,” “evolved Node B,” “eNodeB,” “home Node B,” “home accesspoint,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream to and from a set ofsubscriber stations or provider enabled devices. Data and signalingstreams can comprise packetized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio access network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks comprisebroadcast technologies (e.g., sub-Hertz, extremely low frequency, verylow frequency, low frequency, medium frequency, high frequency, veryhigh frequency, ultra-high frequency, super-high frequency, terahertzbroadcasts, etc.); Ethernet; X.25; powerline-type networking, e.g.,Powerline audio video Ethernet, etc.; femtocell technology; Wi-Fi;worldwide interoperability for microwave access; enhanced general packetradio service; third generation partnership project, long termevolution; third generation partnership project universal mobiletelecommunications system; third generation partnership project 2, ultramobile broadband; high speed packet access; high speed downlink packetaccess; high speed uplink packet access; enhanced data rates for globalsystem for mobile communication evolution radio access network;universal mobile telecommunications system terrestrial radio accessnetwork; or long term evolution advanced.

The term “infer” or “inference” can generally refer to the process ofreasoning about, or inferring states of, the system, environment, user,and/or intent from a set of observations as captured via events and/ordata. Captured data and events can include user data, device data,environment data, data from sensors, sensor data, application data,implicit data, explicit data, etc. Inference, for example, can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events. Inference can also refer to techniquesemployed for composing higher-level events from a set of events and/ordata. Such inference results in the construction of new events oractions from a set of observed events and/or stored event data, whetherthe events, in some instances, can be correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources. Various classification schemes and/or systems(e.g., support vector machines, neural networks, expert systems,Bayesian belief networks, fuzzy logic, and data fusion engines) can beemployed in connection with performing automatic and/or inferred actionin connection with the disclosed subject matter.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A method, comprising: controlling, by a network device of a wireless communication network, activation of a retry functionality for a power saving mode of a device that employs the wireless communication, wherein the network device is operatively coupled to a processor; and controlling, by the network device, a retry threshold value that limits a number of times the device is able to request usage of a device value for a parameter of the power saving mode after having been previously instructed by the network device to use a network value for the parameter.
 2. The method of claim 1, wherein the parameter comprises a duration of an idle mode of the power saving mode.
 3. The method of claim 1, wherein the parameter comprises a duration of a low power mode of the power saving mode.
 4. The method of claim 1, wherein the parameter comprises an active timer for the power saving mode.
 5. The method of claim 1, wherein the controlling the activation and the controlling the retry threshold value comprises sending, by the network device, a control message directing the device to activate the retry functionality in accordance with the retry threshold value.
 6. The method of claim 5, wherein the sending comprises sending the control message as an over the air message.
 7. The method of claim 1, wherein the controlling the activation and the controlling the retry threshold value comprises setting, by the network device, retry functionality parameters for the retry functionality on a subscriber module identity card of the device.
 8. The method of claim 1, further comprising: determining, by the network device, the retry functionality parameters based on a current network condition of the wireless communication network.
 9. The method of claim 8, wherein the current network condition comprises a current load of the network device.
 10. A system, comprising: a processor; and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising: controlling activation of a retry functionality for an power saving mode of a device in association with operation of the device using a wireless communication; and controlling a retry threshold value that limits a number of times the device is permitted to request usage of a device value for a parameter of the power saving mode after having been previously instructed, by a network device of the wireless communication network, to use a network value for the parameter.
 11. The system of claim 10, wherein the parameter comprises a duration of an idle mode of the power saving mode.
 12. The system of claim 10, wherein the parameter comprises a duration of a low power mode of the power saving mode.
 13. The system of claim 10, wherein the controlling the activation and the controlling the retry threshold value comprises sending a control message directing the device to activate the retry functionality in accordance with the retry threshold value.
 14. The system of claim 13, wherein the sending comprises sending the control message as an over the air message.
 15. The system of claim 10, wherein the controlling the activation and the controlling the retry threshold value comprises configuring retry functionality parameters for the retry functionality on a subscriber module identity card of the device.
 16. The system of claim 10, wherein the operations further comprise: determining the retry functionality parameters based on a current network condition of the wireless communication network.
 17. The system of claim 16, wherein the current network condition comprises a current load of the network device.
 18. A non-transitory machine-readable storage medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations, comprising: controlling activation of a retry functionality for an power saving mode of a device in association with usage of a wireless communication by the device; and setting a retry threshold represented by retry threshold data that limits a number of times the device is capable of requesting usage of a device value for a parameter of the power saving mode after having been previously instructed, by a network device of the wireless communication network, to use a network value for the parameter.
 19. The non-transitory machine-readable storage medium of claim 18, wherein the controlling the activation and the setting the retry threshold comprises sending the device an over the air message that directs the device to activate the retry functionality in accordance with the retry threshold.
 20. The non-transitory machine-readable storage medium of claim 18, wherein the controlling the activation and the setting the retry threshold comprises configuring retry functionality parameters for the retry functionality on a subscriber module identity card of the device. 